allow extraVolumes and extraVolumeMounts on core #911
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We've deployed harbor using helm 3 on a 1.18 Kubernetes cluster:
Our storage for the registry, chartmuseum and jobservice is a NFS (ReadWriteMany) solution.
When we access the GUI, the storage gauge on the right appears with a NaN GB.
When using a ReadWriteMany storage solution, I believe this solves this issue: API api/systeminfo/volumes does't work #441
By mounting the same storage as extraVolume on the core component:
Thanks,
Manuel